This functionality has been released in v3.27.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Hi, I would like to ask you, how to manage removing of custom domain.

Scenario:

• 1st run of TF - create
  • create custom domain
  • add id of custom domain to cdn_frontdoor_custom_domain_ids in route
• 2nd run of TF - delete
  • remove custom domain will fail, because is associated to route

So I dont know, how to do it properly.

resource "azurerm_cdn_frontdoor_custom_domain" "domain" {
  name                     = replace(var.name, ".", "-")
  cdn_frontdoor_profile_id = var.frontdoor_profile_id
  dns_zone_id              = var.dns_zone_id
  host_name                = var.name

  tls {
    certificate_type    = "ManagedCertificate"
    minimum_tls_version = "TLS12"
  }
}


resource "azurerm_cdn_frontdoor_route" "route" {

  name                          = "myroute"
  cdn_frontdoor_endpoint_id     = azurerm_cdn_frontdoor_endpoint.endpoint.id
  cdn_frontdoor_origin_group_id = azurerm_cdn_frontdoor_origin_group.group.id
  cdn_frontdoor_origin_ids      = [azurerm_cdn_frontdoor_origin.origins.id]
  cdn_frontdoor_rule_set_ids    = []
  enabled                       = true

  forwarding_protocol    = "HttpsOnly"
  https_redirect_enabled = true
  patterns_to_match      = ["/*"]
  supported_protocols    = ["Http", "Https"]

  cdn_frontdoor_custom_domain_ids = [var.custom_domain_id]
  link_to_default_domain = true

  depends_on = [azurerm_cdn_frontdoor_custom_domain.domain]
}

It baffles me a bit that we have to associate the custom domains to the route using cdn_frontdoor_custom_domain_ids and then we have to associate the routes to the custom domain using resource azurerm_cdn_frontdoor_custom_domain_association.

Surely just the resource azurerm_cdn_frontdoor_custom_domain_association would be enough?

I was also hoping the azurerm_cdn_frontdoor_custom_domain_association resource would be enough but it seems not.

I quote the "Developers Thoughts"

By doing this on the custom domain association resource it could then remove the reference to the custom domain from the route before the custom domain is actually deleted and avoid the FrontDoor service throwing the "custom domain is associated with route" error when deleting the custom domain due to the dependency graph that is generated by Terraform because the custom domain resource does not have a reference to the route

It's not convenient to use

Hi
Can someone please explain a little bit more when and how the resource "azurerm_cdn_frontdoor_custom_domain_association" should be used?

With the provider 3.28.0 I can see that I cannot just use "azurerm_cdn_frontdoor_custom_domain_association" without associating domain earlier in "azurerm_cdn_frontdoor_route" with "cdn_frontdoor_custom_domain_ids "
What is of use of this resource then ? Should I use it in new setup and do I need such a association twice ?

Regards

The association between the custom domain and the routes is only done with the "azurerm_cdn_frontdoor_route" resource and the property "cdn_frontdoor_custom_domain_ids".

The "azurerm_cdn_frontdoor_custom_domain_association" is only used when you remove a custom domain to remove the association with the routes before the custom domain itself is deleting.
Otherwise, you'll receive an error "This resource is still associated with a route. Please delete the association with the route first before deleting this resource".
So, you have to use "azurerm_cdn_frontdoor_custom_domain_association" each time you associate a custom domain to one or multiple routes.

The "azurerm_cdn_frontdoor_custom_domain_association" should contain all routes associated with the custom domain.

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.